[Slack 10.1] OpenOffice.org conflicts with glibc 2.3.4
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I seems to be a bug in OOo, however in Slack 10.0 OOo 1.1.3 and 1.1.4 used to work. I submitted a bug report for OOo. It's issue 43109 in the OOo issue tracker.
This, unfortunately, means that we can't use OOo on Slack 10.1.
Hmm... I'm running Slack 10.1, 2.6.10 kernel, and OOo 1.1.4 on my laptop. It was a wipe HDD/install Slack from CD installation, and OOo is working fine.
For the record, I installed it as root using ./install. It didn't do the GUI install, it just copied/extracted the files to /usr/local. Then I logged in as a user, and ran the setup from the OOo directory, and chose workstation install. Works perfectly.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,646
Rep:
Hi gargamel,
I thought I should write here, because my slackware installation sounds very similar to yours. I have two installations of Slackware, and OpenOffice works under both:
(1) 10.0 upgraded to 10.1 according to Pat's recommendations. OpenOffice.org 1.1.4 (german) was installed under 10.0 but worked without problems after upgrade.
(2) 10.1 installed directly from the cds. OpenOffice 1.1.4 (german) installed after system setup works like a charm, no problem.
So maybe it is not a general problem with the glibc-2.3.4-i486-1.tgz provided on the Slackware cd. Both my installations have only this version. When I start OpenOffice in CLI there is no error message. I hope this helps in finding the cause of the error you encounterd.
I have come across a few reports of people with the same problem that I have, and it appears not to be Slackware specific --- it's also present on some Debian and Red Hat systems, it seems.
On the other hand it works for you...
Maybe, it's not a glibc problem, at all, then. Perhaps I should take the following error message much more seriously, which I get at the time I start the setup script as a regular user for workstation install.
cd /opt/<OOo>/program (as user)
./setup
And here I get this:
libGL error: open DRM failed (Operation not permitted)
libGL error: reverting to (slow) indirect rendering
That sure sounds promising, Ill try it on my gf's comp the next time I get around.. This problem has been driving her nuts.. The thing I dont get, is why does it error with glibc? Sounds pretty much like a windows error.. d:
Originally posted by Artanicus That sure sounds promising, Ill try it on my gf's comp the next time I get around.. This problem has been driving her nuts.. The thing I dont get, is why does it error with glibc? Sounds pretty much like a windows error.. d:
The error message is totally misleading. Without the kind help of the helpful Slackware community and the Slackware maintainer, Patrick Volkerding, I would never have been able to track it down and fix it. Good luck!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.